System and methods for retrieving data using a database configuration file

ABSTRACT

Some embodiments are directed to a method for exchanging data between a user and one or more data sources, the method including configuring a non-transitory computer readable medium to access data from the one or more data sources via a data source query in accordance with options specified in first and second XML configuration files. The non-transitory computer readable medium further retrieves the data in a predefined format at a database and displays the data in accordance with display options specified in the first and the second XML configuration files.

BACKGROUND

The disclosed subject matter relates to data retrieval, and more specifically to a system and methods for displaying data retrieved from data sources on a web portal. In particular, the disclosed subject matter relates to a portal with one or more portlets that are designed to display information from diverse data sources. Retrieved data is typically presented in web pages or web-based graphical user interfaces.

Services relating to data retrieval can be implemented as software components that provide content and/or functionality to remote web applications through the Internet. Remote applications can submit requests for information to web services and receive content in return. Similarly, applications can pass queries to web services by deploying configuration files that contain information regarding the data source, various search filters and display options. A result is returned from the web service to the application based on the queries. Web service content can be passed to a client of the application where it can be displayed, processed, or otherwise utilized.

SUMMARY

Various applications for retrieving data from data sources and displaying the retrieved data on user or client terminals are known. However, each application can retrieve only a specific type of data or data from a specific data source. Further, such applications also need to be present locally on a user or a client terminal.

Some related arts access data from multiple data sources and store the retrieved data in a data warehouse. The data stored on the data warehouse is then displayed on the client or user terminals. However, the data stored in the data warehouse may be in a raw format and further formatting of the data is required before the data can be displayed. Further, data retrieval processes are generally implemented by an application server. An application server can be any software framework that facilitates the creation of web applications and a server environment to run them. It behaves as a virtual machine to run applications and handles connections to data sources on one end and connections to the client terminal or user terminal through a web client or web portal on the other. Often, using only an application server or a cluster of application servers can limit the dynamic delivery of information. Additional processing functions need to be performed by an end-user or client to obtain information in a customized format. Complex client applications are required to process the data retrieved.

Some related arts use applications present on the client terminals to format and display retrieved data. However, such applications format the retrieved data based on predetermined algorithms without providing any option to a user to control the presentation of the retrieved data.

It may therefore be beneficial to provide systems and methods to retrieve data from one or more data sources and display the data in accordance with user-defined display options and data retrieval filters. Specifically, it may be beneficial to generate one or more portlets to facilitate retrieval of data in a legible format without using any applications stored locally on a client or user terminal. One or more portlets are generated by a portal server to facilitate a single point of access to data from data sources for end-users or clients.

It may also be beneficial to provide systems and methods to retrieve data from multiple data sources and store the retrieved data in a database in a predetermined format. The stored data is displayed in accordance with user-defined display options and data retrieval filters without the need for any local applications or programming to format the retrieved data.

It may also be beneficial to provide a specification-compliant, end-user-configurable portlet that allows a user to quickly access and return database data using a portal server and present it in a useful format, without programming. Using a web-interface designed for a non-technical end-user, a series of data-presentation options may be selected or configured and saved to an XML (Extensible Markup Language) configuration file. A portal server, with the portlet installed, may be used to present a view of the data as per the configuration options stored in the XML configuration file. Examples of available configuration options include data retrieval filters, data export formats (XML format, Comma Separated Values or CSV format), and various levels of summary and detail.

It may also be beneficial to provide a specification-compliant, end-user-configurable portlet that allows a user to quickly access and return database data using a portal server and present it in a useful format, without programming. Using a web-interface designed for a non-technical end-user, a series of data-presentation options may be selected or configured and saved to multiple XML configuration files. A set of display options may be saved to a first XML configuration file and a set of data retrieval filters is saved to a second XML configuration file. A portal server, with the portlet installed, may be used to retrieve data as per the set of data retrieval filters stored in the second XML configuration file and present a view of the data as per the display options stored in the first XML configuration file.

It may also be beneficial to provide methods enabling a user to create one or more configuration files which dictate certain display options. For example, each configuration file corresponds to a specific user's desired data feeds and/or display options

Some embodiments are directed to a method for exchanging data between a user and a data source, the method comprising configuring a non-transitory computer readable medium to access at least one set of data from the data source via a data source query in accordance with options specified in a first XML configuration file, the first XML configuration file further specifying a first set of display options, wherein the first XML configuration file is defined by the user. The method further includes selecting a second XML configuration file according to options specified in the first XML configuration file; the second XML configuration file specifying a set of data retrieval filters; retrieving data from the data source in accordance with parameters specified in both the first XML configuration file and the second XML configuration file; storing the data in a database; and displaying the data in accordance with at least one of the first set display options specified in the set of display options specified in the first XML configuration file.

Some other embodiments are directed to a method of retrieving data from a data source, the method comprising receiving a set of display options, a first set of data retrieval filters from a user via a user interface and a selection option, wherein the set of display options and the first set of data retrieval filters correspond to the data source, and wherein the selection option corresponds to a second XML configuration file. The method also includes embedding the first set of data retrieval filters, the set of display options and the selection option into a first XML configuration file. The method further includes selecting the second XML configuration file based on the selection option, the second XML configuration further comprising a second set of data retrieval filters; retrieving a set of data from the data source in accordance with the first set of data retrieval filters embedded in the first XML configuration file and the second set of data retrieval filters specified in the second XML configuration file; storing the set of data in a database in accordance with a predefined format; and generating one or more portlets to display the set of data to the user in accordance with the set of display options.

Yet other embodiments are directed to a system for exchanging data between a user and a data source, the system comprising a portal configured to receive a data source query from the user, the data source query corresponding to a data source; a processor configured to generate a first XML configuration file based on the data source query, the first XML configuration file including a set of display options, a first set of data retrieval filters and a selection option indicative of at least one of a memory location of a second XML configuration file, the second XML configuration further comprising a second set of data retrieval filters; and a portal server communicably coupled to the portal. The portal server is configured to retrieve the second XML configuration file from the memory location specified in the selection option; retrieve a set of data from the data source in accordance with the first set of data retrieval filters embedded in the first XML configuration file and the second set of data retrieval filters specified in the second XML configuration file; store the set of data in a database in accordance with a predefined format; and generate one or more portlets to display the set of data on the portal in accordance with the set of display options.

BRIEF DESCRIPTION OF DRAWINGS

The foregoing and other aspects of the embodiments disclosed herein are best understood from the following detailed description when read in connection with the accompanying drawings. For the purpose of illustrating the embodiments disclosed herein, there is shown in the drawings embodiments that are presently preferred, it being understood, however, that the embodiments disclosed herein are not limited to the specific instrumentalities disclosed. Included in the drawings are the following figures:

FIGS. 1A, 1B and 1C illustrate various exemplary systems for retrieving and displaying data with a Data Integration Portlet in accordance with the disclosed subject matter.

FIG. 2 illustrates the Data Integration Portlet in accordance with the disclosed subject matter.

FIG. 3 is a schematic of a user interface shown on a portal page in accordance with the disclosed subject matter.

FIG. 4 is a flowchart of an exemplary method of retrieving data in accordance with the disclosed subject matter.

FIG. 5 is a flowchart of an exemplary method of retrieving data in accordance with the disclosed subject matter.

FIG. 6 is a computer system that can be used to implement various exemplary embodiments of the disclosed subject matter.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

A few inventive aspects of the disclosed embodiments are explained in detail below with reference to the various figures. Exemplary embodiments are described to illustrate the disclosed subject matter, not to limit its scope, which is defined by the claims. Those of ordinary skill, in the art will recognize a number of equivalent variations of the various features provided in the description that follows.

I. Server Environment

FIG. 1A is an illustration of a system 100 in accordance with the disclosed subject matter. The system 100 is configured to retrieve and display data. Specifically, the system 100 facilitates exchange of data between a user terminal 108 (hereinafter user 108) and one or more data sources 102 through one or more portlets installed on a portal server 104. In some instances, the portal server 104 may be positioned in series with the user terminal, or may even be configured as a part of the user terminal itself (such as an app, OS routine, or the like). The data to be exchanged is retrieved in accordance with an Extensible Markup Language (XML) configuration file that may contain various forms of information. This information can include, but is not limited to, connection information, display preference information, and data source query information. The XML file can also include data retrieval filters, keywords, metadata or metadata tracking information and so forth.

The data sources 102 a to 102 n (hereinafter collectively termed 102) are intended to be any type of data source including social media networks, search engines, portals, remote servers, network storage units, etc. Embodiments are also intended to include or otherwise cover any other type of data source. The data sources 102 are merely provided for exemplary purposes, and the various inventive aspects are intended to be applied to any type of data source on a network 106 connected to a portal server 104 and a user terminal 108 (hereinafter referred to as “the user 108”).

The network 106 may include a data network such as, but not restricted to, the Internet, local area network (LAN), wide area network (WAN), metropolitan area network (MAN), etc. In certain embodiments, the communication network 106 can include a wireless network, such as, but not restricted to, a cellular network and may employ various technologies including enhanced data rates for global evolution (EDGE), general packet radio service (GPRS), global system for mobile communications (GSM), Internet protocol multimedia subsystem (IMS), universal mobile telecommunications system (UMTS) etc. In some embodiments, the communication network 106 may include or otherwise cover networks or subnetworks, each of which may include, for example, a wired or wireless data pathway. The communication network 106 may include a circuit-switched voice network, a packet-switched data network, or any other network capable for carrying electronic communications. For example, the network may include networks based on the Internet protocol (IP) or asynchronous transfer mode (ATM), and may support voice usage, for example, VoIP, Voice-over-ATM, or other comparable protocols used for voice data communications. In one implementation, the network includes a cellular telephone network configured to enable exchange of text or SMS messages.

Examples of the network 106 may further include, but are not limited to, a personal area network (PAN), a storage area network (SAN), a home area network (HAN), a campus area network (CAN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a virtual private network (VPN), an enterprise private network (EPN), Internet, a global area network (GAN), and so forth. Embodiments are intended to include or otherwise cover any type of network, including known, related art, and/or later developed technologies to connect the data sources 102, the portal server 104 and the user 108 with each other.

The user 108 is intended to include any electronic device, such as desktop computers, portable computers, smartphones, tablet computers, wearable devices, and the like. The user 108 may also include a display unit (not shown) for displaying any data. The display unit can include, but not limited to, a Cathode Ray Tube (CRT) display, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and the like. Embodiments are intended to include or otherwise cover any type of display, including known, related art, and/or later developed technologies.

The portal server 104 generates a Data Interchange Portlet 110 (hereinafter DIP) that is a specification-compliant, end-user-configurable portlet that allows a user 108 to quickly access and return database data using a portal server and present it in a useful format, without any substantial programming beyond the generation of the XML configuration file. In some embodiments, the DIP 110 may be part of the user 108, as seen in FIG. 1A. In some other embodiments, the DIP 110 may be part of the portal server 104 (shown in FIG. 1B) or may be placed next to the user 108 (shown in FIG. 1C).

Through a web-interface designed for a non-technical end-user, a series of data-presentation options may be selected (configured) and saved into an XML configuration file. The XML configuration file can also be manually configured. For example, the XML configuration file may be configured in a word processing application. The portal server 104, with the DIP 110 installed, is used to present a view of the data as per the configuration options stored in the XML configuration file. Examples of available configuration options include data retrieval filters, data export formats (XML format, csv format), and various levels of summary and detail. The XML configuration file may include artistic guidelines, such as displaying a three-day weather forecast in the top-left corner of a portal page, and news in the bottom-right corner the portal page. The XML file may also be arbitrarily specific, such as weather in Seattle being displayed in the top left of the portal page, while arrest reports from anyone in Miami named “Edward” being displayed in the bottom right corner of the portal page.

In some embodiments, a processor (not shown) associated with the user 108 may generate the XML configuration file and store it on a memory (not shown) associated with the user 108. Further, the portal server 104 may be communicably coupled to the user 108 in order to access the configuration options stored in the XML configuration file. In other embodiments, the processor that generates the XML configuration file may be associated with the portal server 104.

The portal can be a web portal or an enterprise portal and is configured to aggregate data from different sources and display the aggregated data. In an embodiment, the portal is a web page that brings information together from diverse sources. Each piece of information from a specific source gets a dedicated display or presentation area on the portal as defined by an end-user or web designer. The dedicated display or presentation area is handled or managed by one or more portlets. Portlets are applications used by a data portal website to receive requests from a client terminal or a user terminal and return information. In some embodiments, the portal server 104 is the middleware between an application server (not shown) and the user 108. The portal server 104 can run on top of an application server or a cluster of application servers. The application server or the cluster of application servers can host web applications related to data retrieval.

II. Portals and the Data Integration Portlet

A web portal is a specially designed web site that brings information together from diverse sources in a uniform way. Usually, each information source gets its dedicated area on the page for displaying information (a portlet); often, the end-user can configure which ones to display. Variants of portals include mashups and intranet “dashboards” for executives and managers. The extent to which content is displayed may depend on the intended end-user and the intended purpose, as well as the diversity of the content. Very often design emphasis is on a certain “metaphor” for configuring and customizing the presentation of the content and the chosen implementation framework and/or code libraries. In addition, the role of the end-user in an organization may determine which content can be added to the portal or deleted from the portal configuration.

A portal may use a search engine application program interface (API) to permit end-users to search intranet content as opposed to extranet content by restricting which domains may be searched. Apart from this common search engines feature, web portals may offer other services such as e-mail, news, stock quotes, information from databases and even entertainment content. Portals provide a way for enterprises and organizations to provide a consistent look and feel with access control and procedures for multiple applications and databases, which otherwise would have been different web entities at various uniform resource locators (URL). The features available may be restricted by whether access is by an authorized and authenticated end-user (employee member) or an anonymous site visitor.

Portal servers provide a central platform for accessing web content and resources (data, docs, apps, integrations, alerts, etc.). A core feature of a portal is to provide a central URL that permits an end-user to have a custom web experience based upon the end-users' login identity. This functionality is termed role-based content delivery, or RBCD, and is a main focus for portals.

Websites based on Role-based Content Delivery (RBCD) allow an enterprise to develop a central web platform. Enterprises can then advertise a single website, and thereby increase the usage of the entire enterprise's resources as the central portal can integrate or guide end-users to other resources. RBCD has allowed administrators to build portal pages for different end-user types to customize the end-user experience based on an end-user's “formal identity,” such as a salesperson, engineer or manager.

Given that portal pages can include both applications (portlets and widgets) and web content, many portals have begun supporting integration to an external web content management system (WCMS) allowing content to be created or managed in a WCMS that appears in a portal page. This two-step process of adding content prompted some other portals to create an embedded WCMS.

Portals additionally have begun to focus on end-users, allowing such end-users to interact with the system. End-users are often allowed to create their own pages or sites, to add collaboration apps to those pages and to define end-user access to those pages. Many portals also enable power end-users to have added features, such as web forms, workflows, dynamic lists and polls.

This focus on enabling the end-user, combined with RBCD, allows a central site to enable both the formal organizational structure as well as the informal organizational structure (a.k.a., social collaboration) and is a major difference between portals and many WCMS systems.

FIG. 2 illustrates a system 200 including a Data Integration Portlet (DIP) 204, installed and placed on the portal server 104, in conjunction with the user 108, the data source 210, the data source 212 and/or the data source 214. As illustrated in FIG. 2, the user 108 can create one or more configuration files (1-N as labeled above) which will dictate certain display options. For example, each of a first set of configuration files can correspond to a specific user's desired data feeds and/or display options 202 (e.g., configuration file 1 for John, configuration file 2 for Heather, and so forth). Alternatively, each of the first set of configuration files can correspond to different topics of interest, such as weather forecasts around a country (configuration file 1), political news (configuration file 2), etc. Each of the first set of configuration files can also set the display options that will ultimately appear in the portal page. Each of the first set of configuration files can also point to a second XML configuration file 216, stored on a memory associated with the user 108 or stored on a network storage memory through a selection option. The second XML configuration file 216 is a preset configuration file which can be associated with a data feeds separate from a first XML configuration file created by the user 108. The first XML configuration file can include a first set of display options, a first set of data retrieval filters, a first set of connection information and the selection option in accordance with the user-defined data source query. The second XML configuration file 216 can include a second set of connection information and a second set of data retrieval filters. In some other embodiments, the second XML configuration file can include a second set of display options.

The second XML configuration file 216 can be stored on the network storage memory which includes, but is not limited to, a cloud storage on the internet, a network storage device and the like. Further, the second XML configuration file 216 can also be stored in a memory local to the user 108 or can be uploaded by an end-user from a removable memory device communicably coupled to the user 108. The removable memory can be a flash memory, a floppy disk drive, an optical disc, and so forth.

The user 108 can create queries based on the data to be retrieved. Each query can create one or more configuration files. The queries include, but are not limited to, data retrieval filters, display options and a selection option. The configuration file information includes connection information, display options and data retrieval filters. Connection information includes, but is not limited to, IP addresses, subnet masks, domain name server addresses, host name and suffix, execution parameters, and system information pertaining to the user 108 and/or the portal server 104. Display options include, but are not limited to, at least one of a tabular layout, a chart layout, a news layout, a form layout, and a bullet layout. The data retrieval filters include one or more identities indicative of a data source illustrated in FIG. 2, as the data source 210, the data source 212 and/or the data source 214. The second set of data retrieval filters, included in the second XML configuration file 216, are also indicative of data sources 210, 212 and/or 214. The second set of data retrieval filters can also be indicative of whether the data source specified is a relational database, a key-value store or a document store. Accordingly, parameters indicative of a native language of the specified data source are also included in the second XML configuration file 216. The second XML configuration file therefore provides the configuration information that is used to identify the data source from which data is to be retrieved. The portal server 104 can also determine the phrasing of the query depending on the second set of data retrieval filters. For example, if the data source specified is an IBM Watson™ server, the query transmitted to the WATSON server is a natural language query. The natural language query can be then processed accordingly. Alternatively, if the data source specified in the second XML configuration file 216 is identified to be a Sequential Query Language (SQL) database, the query transmitted to the appropriate data source is parsed accordingly.

In some embodiments, the first and second set of data retrieval filters, and corresponding configuration information embedded in the first and second XML configuration file can also facilitate retrieval of data from multiple data sources concurrently. For example, an end-user may provide a query to the system 200 to retrieve and display pictures of a celebrity from the data source 210, which can be a social network. The query further includes retrieval of pictures of the celebrity with a specific haircut from the data source 212. Accordingly, the first set of data retrieval filters correspond to retrieving data from the data source 210 and the second set of data retrieval filters correspond to retrieving data from the data source 212.

The portal server 104 includes a non-transitory computer readable medium that is configured to access data from the data source 210, the data source 212 and/or the data source 214. In other embodiments, the portal server 104 includes a non-transitory computer readable medium that is configured to access data from multiple data sources not limited to the data source 210, data source 212 and/or data source 214. The non-transitory computer readable medium may be a set of instructions executable by the portal server 104 to carry out various operations including, but not limited to, accessing and retrieving data, storing data, generating portlets and displaying data through the portlets. In some embodiments, the non-transitory computer readable medium can be configured by the portal server 104 to carry out various operations. Further, configuring the non-transitory computer readable medium may include executing the instructions stored therein.

The Data Integration Portlet (DIP) 204 is installed on the portal server 104. One or more XML configuration files provide connection information, a selection option, user-defined display options and data retrieval filters to the portal server 104 using the DIP 204. In some embodiments, the connection information, the selection option, user-defined display options and data retrieval filters form a user-defined data source query. The first XML configuration file containing the user-defined data source query is extracted to a configuration file database 206. The portal server 104, through the DIP 204, further uses the data source query defined by the user 108 to extract data from multiple tables within an information database 208. In some embodiments, the information database 208 may be a relational database and/or an object-relational database. The information database 208 organizes data into one or more tables of columns and rows with a key identifying a row and/or column in each table. The keys for each row and/or column are used to define logical connections (called relationships) among the tables. Based on the user-defined queries, the data residing in the tables are manipulated such that the data is presented at the user 108 in a legible format. The data stored in multiple tables on the information database 208 is retrieved from any or a combination of the data source 210, the data source 212 and/or the data source 214. In some embodiments, the data may be retrieved in real time as per the data source query received at the portal server 104 using the DIP 204. In some other embodiments, the data may have been retrieved before a data source query is received at the portal server 104 using the DIP 204.

In some embodiments, the selection option in the user-defined query is indicative of utilizing display options, connection information and data retrieval filters from the second XML configuration file 216. The selection option is also indicative of a memory location at which the second XML configuration 216 is stored. A second set of connection information and a second set of data retrieval filters specified in the second XML configuration are retrieved and embedded in the first XML configuration file. In other embodiments, the second XML configuration file 216 is extracted to the configuration file database 206.

In some embodiments, the configuration file database 206 may be a relational database that contains the user-defined queries retrieved from the XML configuration files. The data retrieval filters and the display options are stored in one or more tables with a key identifying a row and/or column in each table. The keys are used to define logical connections or relationships among the tables.

The portal server 104 includes a set of software applications that enables generation of portals. The portal server 104 further acts as a single access point for the user 108 to retrieve data from the data source 210, the data source 212 and/or the data source 214. Data extracted by the portal server 104 is stored in an information database 208 in a predefined format. The predefined format corresponds to the data being organized in multiple tables with a key identifying a row and/or column in each table in the data. Logical connections between the rows and columns of one table and the rows and columns of another table

The portal server 104 can transform the data retrieved from the data source 210, the data source 212 and/or the data source 214 in accordance with the predefined format and populate the tables of the database 208 with the data retrieved from the data sources 210, 212 and/or 214. The portal server 104 can implement various algorithms to convert or transform the retrieved data including, but not limited to, including statistical methods, probabilistic methods, and so forth. In case, any data does not include an entry corresponding to any of the tables, the tables are left blank. Therefore, the information database 208 may allow standardization of data from different data sources, and enable quick display of the stored data in accordance with the predefined format, and the set of display options embedded in the first XML configuration file.

In an embodiment, the user queries, the display options and the data retrieval filters may be obtained via a user interface which will be described in detail hereinafter.

FIG. 3 illustrates an exemplary embodiment of a user interface 300 presented on the user 108. The user interface 300 includes fields for various query parameters. The fields include, but are not limited to, a body field 302, a username field 304, query creation dates field 306, a query title or case field 308, a language filter field 310, date/time stamp details field 312, a data source field 314, location filters field 316, authenticate filters field 318, a selection field 320 for enabling additional configuration options through a second XML configuration file and a field 324 for hyperlink filters. Results are displayed according to choices made in the aforementioned fields at a results field 326. The radio button 322 is utilized to provide location details pertaining to the second XML configuration file. In some embodiments, the radio button 322 leads to a dialog window or an additional form on which details pertaining to the location of the second XML configuration file is given by an end-user. In some other embodiments, the second XML configuration file is selected by default by the portal server 104.

In some embodiments, the results field 326 is associated with one or more portlets. Each of the fields 302 to 324 and the results field 326 correspond to one or more portlets generated by the portal server 104. Further, the results are displayed through a first portlet 326 a and a second portlet 326 b. The portlet 326 a and the portlet 326 b may be generated by the portal server 104.

Choices made on the user interface 300 form the data source query and is embedded into a first Extensible Markup language (XML) configuration file stored on the user 108. An example of the information stored in the first XML configuration file is shown below:

<QuerySettings> <DatabaseVendor>PostgreSQL</DatabaseVendor> <Connection> <ConnectionID>2</ConnectionID> </Connection> <QueryString>SELECT verifiedimg, verifiedyn, username, displayname, authorkloutscore, useractivitycount, friends, followers, listedcount, favoritescount, retweetcount, generator, verified, profileimgurl, network, created, createdyear, createdmonth, createdday, body, isre, origobjsrcid, objectsrcunid, origauthor, sourceid, hashtags, languages, expandedurls, verb, usermentionsnames, usermentionsids, mediaurls, lon, lat, headline, tagline, createdby, objectcreateddate, geocoordinates, linktoobject, resultid, Geocoded, globe, resultid, id, userbiolocation, mediatype, usermentionsscreennames, actorid, verified, userbiolocation, sentiment_tag, sentiment_score, user_sentiment_votes, user_sentiment_average, user_sentiment_mode, user_sentiment_median, mediayn, tsv_body

The above is a snippet from the exemplary first XML configuration file used in accordance with the disclosed subject matter. Each of the first XML configuration files uses a single query extracted from the input through the user interface 300 to retrieve data from multiple tables within the information database 208.

The first XML configuration file is used for the processing, definition and presentation of data on the user interface 300. Through the first XML configuration file, code is specified for formatting various layouts and styles pertaining to presentation of data. The first XML configuration file, as seen in the sample code above, includes the user-defined query, that further includes selection options, a first set of communication information, a first set of display options and a first set of data retrieval filters, as illustrated in FIG. 2. The first XML configuration file provides connection information to enable a connection between the user 108 and the information database 208 (in the current example the information database 208 being an object-relational database provided by PostgreSQL®). Further, a selection option enabling the extraction of a second set of communication information and/or a second set of data retrieval filters from the second XML configuration file is provided. In some embodiments, the selection option may enable the extraction of a second set of display options. The selection option includes a flag to enable of selection of the second XML configuration file and file location details pertaining to the second XML configuration file. In some embodiments, the second XML configuration file can use XML code similar to the aforementioned snippet. In the above snippet, the “Querystring” tag provides the multiple fields shown in FIG. 3 as the fields 302 to 324.

In an exemplary embodiment, the data source query including the first set of display options, the first set of data retrieval filters and the first set of communication information specified in the first XML configuration file is augmented with the second set of display filters, the second set of data retrieval filters and the second set of communication information specified in the second XML configuration file. Data is retrieved from the data source 210, the data source 212 and/or the data source 214 in accordance with the augmented data source query. For example, the first XML configuration file may specify that data retrieved from the data source 210 is to be shown in the first portlet 326 a, while the second XML configuration file may specify that data retrieved from the data source 212 is to be shown in the second portlet 326 b. Therefore, the portal server 104 can use the augmented data source query based on a combination of the first and second XML configuration files, and display the data retrieved from the data sources 210 and 212 in the first and second portlets 326 a, 326 b, respectively.

In some embodiments, the selection option in the first XML configuration file further comprises a priority option that is indicative of a priority between the first XML configuration file and the second XML configuration file. The priority option may be displayed in a form based interface after an end-user has selected the selection field 320. The portal server 104 identifies the sets of display options and the sets of data retrieval filters common to the first XML configuration file and the second XML configuration file. Based on the priority indicated, the portal server 104 selects the appropriate set of data retrieval filters and the set of display options. For example, both the first XML configuration file and the second XML configuration file may indicate that the data retrieved is to be displayed in the first portlet 326 a. However, according to the first set of data retrieval filters, data is to be retrieved from the data source 212, while the second set of data retrieval filters direct the data to be retrieved from the data source 210. With the priority option indicating that the first XML configuration file supersedes the second XML configuration file, the portal server 104 displays the data retrieved from data source 212 at the first portlet 326 a and the data retrieved from the data source 210 at the second portlet 326 b.

The first XML configuration file and the second XML configuration file further act as tools to transport the user-defined query information from the user 108 to the configuration file database 206 and the information database 208. Subsequently, based on the user-defined query, the portal server 104 extracts the data corresponding to the retrieval filters specified at the fields 302 to 324 from the data source specified at the data source field 314. The data is extracted in a predefined format at the information database 208. Subsequently, the extracted data is presented based on the display options specified in the user-defined query through the portlets corresponding to the results field 326 as shown in FIG. 3.

In order for a single query, such as that shown in the XML sample above, to retrieve data from multiple sources, the data would need to exist in any of the data source 210, the data source 212 and/or the data source 214 and in the information database 208 specified in the query.

The database connection details or connection information, such as that referenced in the XML code above, are specified in the first XML configuration file and/or in the second XML configuration file. In some embodiments, the connection information in the first and second XML configuration files may be combined to access the data.

III. Exemplary Embodiments

In an exemplary embodiment, a first XML configuration file is generated at the user 108 with a user-defined query embedded. The user-defined query includes a first set of connection information, a selection option, a first set of data retrieval filters and a first set of display options. As shown in FIG. 3, the fields 302 to 324 in the user interface 300 are populated such that user-defined options relating to the selection option, the first set of data retrieval filters and the first set of display options are specified. The user interface 300 is displayed on a display interface (not shown) that is included with the user 108. In accordance with the sample XML code above, the populated fields 302 to 324 enable selections of the query strings such that the first data source query is created and embedded into the first XML configuration file.

Using the DIP 204 that is installed on the portal server 104, the first user-defined query, along with other configuration information contained in the first XML configuration file, is transmitted to the configuration file database 206. If the selection field 320 is enabled and location details for a second XML configuration file is provided by an end-user through the radio button 322, the configuration information from the second XML configuration file including a second set of display options, and/or a second set of data retrieval filters, is extracted to the configuration file database 206 along with the user-defined query from the first XML configuration file.

The second XML configuration file provides the configuration information that is used to identify the data sources 210, 212 and/or 214. The first set of data retrieval filters and corresponding configuration information embedded in the first XML configuration file and the second set of data retrieval filters and corresponding configuration information embedded in the second XML configuration file facilitate the retrieval of data from multiple data sources concurrently. For example, an end-user may provide a query to the system 200 to retrieve and display pictures of a celebrity from the data source 210, which can be a social network. The query further includes retrieval of pictures of the celebrity with a specific haircut from the data source 212. Accordingly, the first set of data retrieval filters correspond to retrieving data from the data source 210 and the second set of data retrieval filters correspond to retrieving data from the data source 212.

The information database 208, as shown in FIG. 2, stores data retrieved from the data source 210, the remote data source 212 and/or the remote data source 214 in accordance with the first XML configuration file and the second XML configuration file. The data may be retrieved prior to the user-defined query and the configuration information being received at the configuration file database 206. In some embodiments, the data may be retrieved upon receiving the user-defined query and the configuration information. The retrieved data is stored on the information database 208 in a predefined format. The predefined format includes the retrieved data being stored in multiple tables with each row and/or column of each table being identified by a key. The keys are used to establish logical connections between rows and columns of one table in the information database 208 with the rows and columns of another table in the information database 208.

Based on the user-defined query stored in the tables of the configuration file database 206, retrieved data, corresponding to any one of the data source 210, the data source 212 and/or the data source 214, is extracted from the tables of the information database 208 and presented on the user interface 300 (as shown in FIG. 3) at the portlets corresponding to the results field 326.

Some embodiments, in accordance with the disclosed subject matter, are directed to the system 100 that facilitates exchange of a data between the data sources 102 and the user 108, using one or more portlets installed on a portal server 104. A first XML configuration file containing a data source query is generated at the user 108. The data source query includes a first set of data retrieval filters, a first set of display options and a selection option. Based on the selection option, a second XML configuration file is selected, the second XML configuration file specifying a second set of data retrieval filters and a second set of display options. The portal server 104 may retrieve and display data based on the first set of data retrieval filters, the first set of display options, the second set of data retrieval filters and/or the second set of display options.

FIG. 4 illustrates a method 400 of retrieving data from one or more remote data source in accordance with the disclosed subject matter. This flowchart is merely provided for exemplary purposes, and embodiments are intended to include or otherwise cover any methods or procedures for data retrieval.

In accordance with the flowchart of FIG. 4, at step 402, a non-transitory computer readable medium is configured to access a set of data from a remote data source based on a data source query specified in a first user-defined XML configuration file. The portal server 104 may configure the non-transitory computer readable medium. In some embodiments, a processor (not shown) associated with the user 108 generates the first XML configuration file and stores it on a memory (not shown) associated with the user 108. The portal server 104 includes the non-transitory computer readable medium. The data source may be selected through choices on the form-based user interface 300 and the choices are embedded into the first XML configuration file stored on the user 108. The choices include a first set of connection information, a first set of display options, a first set of data retrieval filters and a selection option.

At step 404, using the selection option, a second XML configuration file is selected and extracted to the configuration file database 206. The second XML configuration file further includes a second set of connection information, a second set of display options and a second set of data retrieval filters. At step 406, data is retrieved from a data source in accordance with parameters specified in both the first and second XML configuration files. The parameters can include the first and second sets of data retrieval filters and/or the first and second sets of display options. At step 408, the retrieved data is stored in tables of the information database 208 in accordance with a predefined format. The predefined format is a presentation format that may be implemented in accordance with the display options made available through the XML configuration file and subsequently the form-based user interface 300. Such a format facilitates data retrieval processes in a customized presentation as defined by the user 108. The data stored in the information database 208 is extracted and presented on the user interface 300 through the user 108.

At step 410, the requested information requested is displayed accordingly. FIG. 2 further illustrates an exemplary embodiment of the aforementioned process wherein information is sought from a data source concerning a subject or topic with other filters implemented. At the selection field 320, the option for utilizing configuration information from the second XML configuration file is enabled. The radio button 322 may direct to one or more associated forms that are used to provide location details for the XML configuration file. Data is retrieved from one or more data sources in accordance with both the first and second XML configuration files. Further, the retrieved data is displayed at the portlets 326 a and 326 b in accordance with the first and second display options in the first and second XML configuration files, respectively.

In various embodiments, one or more of the steps 402 to 410 may be implemented by the portal server 104 as per instructions provided in the non-transitory computer readable medium.

FIG. 5 is a flowchart of a method 500 for retrieving data from one or more data sources in accordance with the disclosed subject matter. Through the form-based user interface 300, a data source query is received at step 502. The data source query includes a first set of data retrieval filters, a first set of display options, a first set of connection information and a selection option.

At step 504, the retrieval filters and display options are embedded in the XML configuration file. The configuration file information further includes connection information which constitute any one or a combination of IP addresses, subnet masks, domain name server addresses, host name and suffix, execution parameters, and system information pertaining to the user 108 and/or the portal server 104. At step 506, the selection option is used to select a second XML configuration file. The second XML configuration file includes a second set of data retrieval filters, a second set of connection information and a second set of display options. At step 508, data is retrieved in accordance with first and second sets of data retrieval filters specified in the first and second XML configuration files, respectively. At step 510, the retrieved data is stored in a predefined format in the information database 208. The predefined format includes all of the display options made available to the user 108 in accordance with the first and second XML configuration files.

Further, at step 512, the retrieved data is displayed at the first portlet 326 a and the second portlet 326 b on the user interface 300 in accordance with the first set of display options, the second set of display options and the predefined format. In some other embodiments, the generated portlet leads to a new web page showing the retrieved data. The first and second portlets 326 a, 326 b may be generated by the portal server 104.

In various embodiments, one or more of the steps 502 to 512 may be implemented by the portal server 104 as per instructions provided in the non-transitory computer readable medium.

IV. Other Exemplary Embodiments

FIG. 6 illustrates a computer system 600 upon which the operation of the user 108, the DIP 204, the configuration file database 206, the information database 208 and the portal server 104 may be implemented. Although, the computer system 600 is depicted with respect to a particular device or equipment, it is contemplated that other devices or equipment (e.g., network elements, servers, etc.) within FIG. 6 can deploy the illustrated hardware and components of system. The computer system 600 is programmed (e.g., via computer program code or instructions) to retrieve data from the data sources 102 described herein and includes a communication mechanism such as a bus 602 for passing information between other internal and external components of the computer system 600. Information (also called data) is represented as a physical expression of a measurable phenomenon, typically electric voltages, but including, in other embodiments, such phenomena as magnetic, electromagnetic, pressure, chemical, biological, molecular, atomic, sub-atomic and quantum interactions. For example, north and south magnetic fields, or a zero and non-zero electric voltage, represent two states (0, 1) of a binary digit (bit). Other phenomena can represent digits of a higher base. A superposition of multiple simultaneous quantum states before measurement represents a quantum bit (qubit). A sequence of one or more digits constitutes digital data that is used to represent a number or code for a character. In some embodiments, information called analog data is represented by a near continuum of measurable values within a particular range. The computer system 600, or a portion thereof, constitutes a means for performing one or more steps retrieving data from one or more data sources 102.

A bus 602 includes one or more parallel conductors of information so that information is transferred quickly among devices coupled to the bus 602. A processor 704 for processing information are coupled with the bus 602.

The processor 604 performs a set of operations on information as specified by a user. The computer program code is a set of instructions or statements providing instructions for the operation of the processor 604 and/or the computer system 600 to perform specified functions. The code, for example, may be written in a computer programming language that is compiled into a native instruction set of the processor 604. The code may also be written directly using the native instruction set (e.g., machine language). The set of operations include bringing information in from the bus 602 and placing information on the bus 602. The set of operations also typically include comparing two or more units of information, shifting positions of units of information, and combining two or more units of information, such as by addition or multiplication or logical operations like OR, exclusive OR (XOR), and AND. Each operation of the set of operations that can be performed by the processor is represented to the processor by information called instructions, such as an operation code of one or more digits. A sequence of operations to be executed by the processor 604, such as a sequence of operation codes, constitute processor instructions, also called computer system instructions or, simply, computer instructions. The processor 604 may be implemented as mechanical, electrical, magnetic, optical, chemical, or quantum components, among others, alone or in combination.

The computer system 600 also includes a memory 606 coupled to the bus 602. The memory 606, such as a Random Access Memory (RAM) or any other dynamic storage device, stores information including processor instructions for storing information and instructions to be executed by the processor 604. The dynamic memory 606 allows information stored therein to be changed by the computer system 600. RAM allows a unit of information stored at a location called a memory address to be stored and retrieved independently of information at neighboring addresses. The memory 606 is also used by the processor 604 to store temporary values during execution of processor instructions. The computer system 600 also includes a Read Only Memory (ROM) or any other static storage device coupled to the bus 602 for storing static information, including instructions, that is not changed by the computer system 600. Some memory is composed of volatile storage that loses the information stored thereon when power is lost. Also coupled to the bus 602 is a non-volatile (persistent) storage device 608, such as a magnetic disk, a solid state disk, optical disk or flash card, for storing information, including instructions, that persists even when the computer system 600 is turned off or otherwise loses power.

Information, including instructions for inspecting the XML data source query files is provided to the bus 602 for use by the controller 604 from an external input/output device 610. From an input perspective, the input/output device could include one or more elements such as a keyboard containing alphanumeric keys operated by a human user, a mouse, trackball, microphone, an Infrared (IR) remote control, a joystick, a game pad, a stylus pen, a touch screen, or any other of an input/output device. These devices can be capable of controlling a position of a small cursor image presented on the display 612 and issuing commands associated with graphical elements presented on the display 612.

From an output perspective, the input/output device 610 could include a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, an organic LED (OLED) display, an active matrix display, an Electrophoretic Display (EPD), a plasma screen, or a printer for presenting text or images. Additionally, a separate display 612 may also include any of the previously mentioned devices or any other devices capable of visually, audibly, or even by means of touch, scent, etc., to provide output data to a user. Further, the display 612 may be a touch enabled display such as capacitive or resistive screen. In some embodiments, for example, in embodiments in which the computer system 600 performs all functions automatically without human input, one or more of the external input device 610, and the display 612 may be omitted.

Sensors 614 may be provided as components of the input/output device 610, or may be provided as independent components to the system 600. The sensor(s) 614 may detect conditions in its vicinity and transform those detections into physical expressions compatible with the measurable phenomenon used to represent information in the computer system 600 such as capturing, recording and causing to store one or more still and/or moving images (e.g., videos, movies, etc.) which also may comprise audio recordings. Sensors 614 may also detect elements such as motion, temperature, imagery or video, etc.

Other external devices can also be coupled to the bus 602 such as an Application Specific IC (ASIC) device 616. In the illustrated embodiment, special purpose hardware such as the ASIC 616 might serve as special purpose hardware configured to perform operations not performed by the controller 604 quickly enough for various purposes. Examples of ASICs include graphics accelerator cards for generating images for the display 612, cryptographic boards for encrypting and decrypting messages sent over a network, speech recognition, and interfaces to special external devices, such as robotic arms and medical scanning equipment that repeatedly perform some complex sequence of operations that are more efficiently implemented in hardware.

The computer system 600 also includes one or more instances of a communication interface 618 coupled to the bus 602. The communication interface 618 provides a one-way or two-way communication coupling to a variety of external devices that operate with their own processors, such as printers, scanners and external disks. In general, the coupling is with a network link 620 that is connected to a local network 622 to which a variety of external devices with their own processors are connected. For example, the communication interface 618 may be a parallel port or a serial port or a Universal Serial Bus (USB) port on a personal computer. In some embodiments, the communication interface 618 is an Integrated Services Digital Network (ISDN) card, a Digital Subscriber Line (DSL) card, or a telephone modem that provides an information communication connection to a corresponding type of a telephone line. In some embodiments, the communication interface 618 is a cable modem that converts signals on the bus 602 into signals for a communication connection over a coaxial cable or into optical signals for a communication connection over a fiber optic cable. As another example, the communication interface 618 may be a Local Area Network (LAN) card to provide a data communication connection to a compatible LAN, such as Ethernet™ or an Asynchronous Transfer Mode (ATM) network. In one embodiment, wireless links may also be implemented. For wireless links, the communication interface 618 sends or receives or both sends and receives electrical, acoustic or electromagnetic signals, including infrared and optical signals that carry information streams, such as digital data. For example, in wireless handheld devices, such as mobile telephones like cell phones, the communication interface 618 includes a radio band electromagnetic transmitter and receiver called a radio transceiver. In certain embodiments, the communication interface 618 enables connection to the communication network 106 for inspecting the user queries in the XML configuration files. Further, the communication interface 618 can include peripheral interface devices, such as a thunderbolt interface, a Personal Computer Memory Card International Association (PCMCIA) interface, etc. Although a single communication interface 618 is depicted, multiple communication interfaces can also be employed.

The term “computer-readable medium” as used herein refers to any medium that participates in providing information to the processor 604, including instructions for execution. Such a medium may take many forms, including, but not limited to, computer-readable storage medium (e.g., non-volatile media, volatile media), and transmission media. Non-transitory media, such as non-volatile media, include, for example, optical or magnetic disks, such as the storage device 608. Volatile media include, for example, the dynamic memory 606. Transmission media include, for example, twisted pair cables, coaxial cables, copper wire, fiber optic cables, and carrier waves that travel through space without wires or cables, such as acoustic waves, optical or electromagnetic waves, including radio, optical and infrared waves. Signals include man-made transient variations in amplitude, frequency, phase, polarization or other physical properties transmitted through the transmission media. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a USB flash drive, a Blu-ray disk, a CD-ROM, CDRW, DVD, any other optical medium, punch cards, paper tape, optical mark sheets, any other physical medium with patterns of holes or other optically recognizable indicia, a RAM, a PROM, an EPROM, a FLASH-EPROM, an EEPROM, a flash memory, any other memory chip or cartridge, a carrier wave, or any other medium from which a computer can read. The term computer-readable storage medium is used herein to refer to any computer-readable medium except transmission media.

Logic encoded in one or more tangible media includes one or both of processor instructions on a computer-readable storage media and special purpose hardware, such as ASIC 616.

The network link 620 typically provides information communication using transmission media through one or more networks to other devices that use or process the information. For example, the network link 620 may provide a connection through the local network 622 to a host computer 624 or to ISP equipment operated by an Internet Service Provider (ISP).

A server 626, connected to the Internet, hosts a process that provides a service in response to information received over the Internet. For example, the server 626 hosts a process that provides information representing video data for presentation at the display 612. It is contemplated that the components of the computer system 600 can be deployed in various configurations within other computer systems, e.g., the host 624 and the server 626.

At least some embodiments of the invention are related to the use of the computer system 600 for implementing some or all of the techniques described herein. According to one embodiment of the invention, those techniques are performed by the computer system 600 in response to the processor 604 executing one or more sequences of one or more processor instructions contained in the memory 606. Such instructions, also called computer instructions, software and program code, may be read into the memory 606 from another computer-readable medium such as the storage device 608 or the network link 620. Execution of the sequences of instructions contained in the memory 606 causes the processor 604 to perform one or more of the method steps described herein. In alternative embodiments, hardware, such as the ASIC 616, may be used in place of or in combination with software to implement the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware and software, unless otherwise explicitly stated herein.

Various forms of computer readable media may be involved in carrying one or more sequence of instructions or data or both to the processor 604 for execution. For example, instructions and data may initially be carried on a magnetic disk of a remote computer such as the host 624. The remote computer loads the instructions and data into its dynamic memory and sends the instructions and data over a telephone line using a modem. A modem local to the computer system 600 receives the instructions and data on a telephone line and uses an infra-red transmitter to convert the instructions and data to a signal on an infra-red carrier wave serving as the network link 620. An infrared detector serving as the communication interface 618 receives the instructions and data carried in the infrared signal and places information representing the instructions and data onto the bus 602. The bus 602 carries the information to the memory 606 from which the processor 604 retrieves and executes the instructions using some of the data sent with the instructions. The instructions and data received in the memory 606 may optionally be stored on the storage device 608, either before or after execution by the processor 604.

V. Alternative Embodiments

While certain embodiments of the invention are described above, and FIGS. 1A-6 disclose the best mode for practicing the various inventive aspects, it should be understood that the invention can be embodied and configured in many different ways without departing from the spirit and scope of the invention.

For example, embodiments are disclosed above in the context of retrieving data from one or more data sources based on user queries embedded in XML configuration files. However, embodiments are intended to include or otherwise cover any type of configuration file.

Embodiments as disclosed above allow retrieval of data from different data sources and display the data as per user-defined display options and data retrieval filters through a portal server and an associated portal. Embodiments of the present disclosure further enable the portal server to be a single point of access in data retrieval and display without using any additional resources or applications on an end-user terminal.

Embodiments, as disclosed above, are directed to the system 100 that facilitates exchange of one or more sets of data between the data sources 102 and the user 108, using one or more portlets installed on a portal server 104. A first XML configuration file containing a data source query is generated at the user 108. The data source query includes a first set of data retrieval filters, a first set of display options, a first set of connection information and a selection option. The selection option is directed toward a second XML configuration file 216 that is stored on a memory communicably coupled with the network 106 or a removable memory communicably coupled with the user 108. The second XML configuration file 216 includes a second set of data retrieval filters, a second set of display options and a second set of connection information. The system 100 facilitates exchange of data between the user 108 and the data sources 102 through one or more portlets installed on the portal server 104 in accordance with the first and second XML configuration files. The second set of display options, the second set of data retrieval filters and the second set of communication information may augment the data source query embedded in the first XML configuration file. It may not be necessary to fill out one or more of the fields 302 to 318 and the field 324 as one or more of these parameters may be extracted from the second XML configuration file 216 and data retrieved accordingly.

Embodiments are also intended to cover processing a data source query using two or more XML configuration files. A first XML configuration file containing a data source query is generated at the user 108. The data source query includes a first set of data retrieval filters, a set of display options, a first set of connection information and a selection option. The selection option is directed toward a second XML configuration file 216 that is stored on a memory communicably coupled with the network 106 or a removable memory communicably coupled with the user 108. The second XML configuration file 216 includes a second set of data retrieval filters and a second set of connection information. The second XML configuration file provides the configuration information that is used to identify the data sources 210, 212 and/or 214. The first set of data retrieval filters and corresponding configuration information embedded in the first XML configuration file, and the second set of data retrieval filters and corresponding configuration information embedded in the second XML configuration file facilitate the retrieval of data from multiple data sources concurrently.

Embodiments are also intended to cover storing retrieved data in any predefined format in a database associated with the portal server such that the data can be displayed through portlets generated by the portal server. The predefined format can be based on a type of data source and user-defined data fields provided in an XML configuration file.

Embodiments are also intended to cover any form building toolkit that allows creation of forms without coding for a portal page. The forms can be used to receive options from a user and display data.

Exemplary embodiments are intended to cover all software or computer programs capable of enabling processors to implement the above operations, designs and determinations. Exemplary embodiments are also intended to cover any and all currently known, related art or later developed non-transitory recording or storage mediums (such as a CD-ROM, DVD-ROM, hard drive, RAM, ROM, floppy disc, magnetic tape cassette, etc.) that record or store such software or computer programs. Exemplary embodiments are further intended to cover such software, computer programs, systems and/or processes provided through any other currently known, related art, or later developed medium (such as transitory mediums, carrier waves, etc.), usable for implementing the exemplary embodiments disclosed above.

In accordance with the exemplary embodiments, the disclosed computer programs can be executed in many exemplary ways, such as an application that is resident in the memory of a device or as a hosted application that is being executed on a server and communicating with the device application or browser via a number of standard protocols, such as TCP/IP, HTTP, XML, SOAP, REST, JSON and other sufficient protocols. The disclosed computer programs can be written in exemplary programming languages that execute from memory on the device or from a hosted server, such as BASIC, COBOL, C, C++, Java, Pascal, or scripting languages such as JavaScript, Python, Ruby, PHP, Perl or other sufficient programming languages.

Some of the disclosed embodiments include or otherwise involve data transfer over a network, such as communicating various inputs over the network. The network may include, for example, one or more of the Internet, Wide Area Networks (WANs), Local Area Networks (LANs), analog or digital wired and wireless telephone networks (e.g., a PSTN, Integrated Services Digital Network (ISDN), a cellular network, and Digital Subscriber Line (xDSL)), radio, television, cable, satellite, and/or any other delivery or tunneling mechanism for carrying data. Network may include multiple networks or subnetworks, each of which may include, for example, a wired or wireless data pathway. The network may include a circuit-switched voice network, a packet-switched data network, or any other network able to carry electronic communications. For example, the network may include networks based on the Internet protocol (IP) or asynchronous transfer mode (ATM), and may support voice using, for example, VoIP, Voice-over-ATM, or other comparable protocols used for voice data communications. In one implementation, the network includes a cellular telephone network configured to enable exchange of text or SMS messages.

Examples of a network include, but are not limited to, a personal area network (PAN), a storage area network (SAN), a home area network (HAN), a campus area network (CAN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a virtual private network (VPN), an enterprise private network (EPN), Internet, a global area network (GAN), and so forth.

While the subject matter has been described in detail with reference to exemplary embodiments thereof, it will be apparent to one skilled in the art that various changes can be made, and equivalents employed, without departing from the scope of the invention. All related art references discussed in the above Background section are hereby incorporated by reference in their entirety. 

What is claimed is:
 1. A method for exchanging data between a user and a data source, the method comprising: configuring a non-transitory computer readable medium to access at least one set of data from the data source via a data source query in accordance with options specified in a first XML configuration file, the first XML configuration file further specifying a set of display options, wherein the first XML configuration file is defined by the user; selecting a second XML configuration file according to options specified in the first XML configuration file, the second XML configuration file specifying a set of data retrieval filters, and; retrieving data from the data source in accordance with parameters specified in both the first XML configuration file and the second XML configuration file; storing the data in a database, and displaying the data in accordance with at least one of the set display options specified in the first XML configuration file.
 2. The method of claim 1 further comprising: identifying one or more options specified in the first XML configuration file indicative of a selection of the second XML configuration file; receiving an identifier from the user indicative of at least a memory location of the second XML configuration file; and retrieving the second XML configuration file based on the identifier received from the user.
 3. The method of claim 2, wherein the identifier is specified in the first XML configuration file.
 4. The method of claim 2, further comprising: identifying a priority option specified in the first XML configuration file indicative of a priority between the first XML configuration file and the second XML configuration file; identifying options related to parameters common to both the first XML configuration file and the second XML configuration file; and selecting the options specified in the first XML configuration file or the options specified in the second XML configuration file based on the priority option.
 5. The method of claim 1, wherein the parameters comprise a first set of data retrieval filters specified in the first XML configuration and a second set of data retrieval filters specified in the second XML configuration file.
 6. The method of claim 1, further comprising displaying the set of data on one or more portlets on a portal page.
 7. The method of claim 1, further comprising receiving the data source query from a portal page.
 8. The method of claim 1, further comprising storing the first XML configuration file in a memory local to the user.
 9. The method of claim 1, wherein the data source query comprises one or more identities indicative of the data source, one or more sets of keywords, and the set of display options.
 10. The method of claim 1, further comprising: transforming the data retrieved from the data source in accordance with a predefined format; and storing the set of data transformed to the predefined format in a server database.
 11. The method of claim 1, further comprises accessing connection information stored in the second XML configuration file to retrieve the set of data.
 12. A method of retrieving data from a data source, the method comprising: receiving a set of display options, a first set of data retrieval filters and a selection option from a user via a user interface, wherein the set of display options and the first set of data retrieval filters correspond to the data source, and wherein the selection option corresponds to a second XML configuration file; embedding the first set of data retrieval filters, the set of display options and the selection option into a first XML configuration file; selecting the second XML configuration file based on the selection option, the second XML configuration further comprising a second set of data retrieval filters; retrieving a set of data from the data source in accordance with the first set of data retrieval filters embedded in the first XML configuration file and the second set of data retrieval filters specified in the second XML configuration file; storing the set of data in a database in accordance with a predefined format; and generating one or more portlets to display the set of data to the user in accordance with the set of display options.
 13. The method of claim 12, wherein the selection option comprises an identifier indicative of at least one of a memory location of the second XML configuration file, the method further comprising retrieving the second XML configuration file based on the identifier specified in the selection option.
 14. The method of claim 12, further comprising: identifying a priority option specified in the first XML configuration file indicative of a priority between the first XML configuration file and the second XML configuration file; identifying options related to parameters common to both the first XML configuration file and the second XML configuration file; and selecting the options specified in the first XML configuration file or the options specified in the second XML configuration file based on the priority option.
 15. The method of claim 12, further comprising storing the first XML configuration file in a memory local to the user.
 16. The method of claim 12, further embedding one or more identities of the data source and one or more sets of keywords in the first XML configuration file.
 17. A system for exchanging data between a user and a data source, the system comprising: a portal configured to receive a data source query from the user, the data source query corresponding to a data source; a processor configured to generate a first XML configuration file based on the data source query, the first XML configuration file including a set of display options, a set of data retrieval filters and a selection option indicative of at least one of a memory location of a second XML configuration file, the second XML configuration further comprising a second set of data retrieval filters; and a portal server communicably coupled to the portal, the portal server configured to: retrieve the second XML configuration file from the memory location specified in the selection option; retrieve a set of data from the data source in accordance with the first set of data retrieval filters embedded in the first XML configuration file and the second set of data retrieval filters specified in the second XML configuration file; store the set of data in a database in accordance with a predefined format; and generate one or more portlets to display the set of data on the portal in accordance with the set of display options.
 18. The system of claim 17, wherein the portal server is further configured to access connection information stored in the first XML configuration file and the second XML configuration file to retrieve the set of data.
 19. The system of claim 17, wherein the portal server is further configured to identify a priority option specified in the first XML configuration file indicative of a priority between the first XML configuration file and the second XML configuration file; identify options related to parameters common to both the first XML configuration file and the second XML configuration file; and select the options specified in the first XML configuration file or the options specified in the second XML configuration file based on the priority option.
 20. The system of claim 17, wherein the processor is further configured to store the first XML configuration file in a memory local to the user. 